DRU-708 -- Read deployment secrets from files - #65
Merged
czpython merged 1 commit intoOct 3, 2026
Merged
Conversation
czpython
changed the title
czpython
force-pushed
the
paulo/dru-708-read-drukbox-deployment-secrets-from-files
branch
from
October 3, 2026 13:53
ae7cc32 to
a6f7939
Compare
A process reads a setting from /run/secrets/<NAME> when that directory exists, so a deployment can keep secrets out of the environment. The provider settings also hide their input in startup errors.
czpython
force-pushed
the
paulo/dru-708-read-drukbox-deployment-secrets-from-files
branch
from
October 3, 2026 13:57
a6f7939 to
d138fac
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A process reads a setting from a file in
/run/secretswhen that directory exists. The file name is the variable name, for example/run/secrets/DATABASE_URL. Compose file secrets mount there, so a deployment can keep its secrets out ofdocker inspectand out of the environment that subprocesses inherit..enventry still wins over a file.hide_input_in_errors, like the core settings. A missing Tailscale value no longer printsTAILSCALE_OAUTH_CLIENT_SECRETin the startup error.docs/deploy.mdhas a new "Secret files" section: file names, precedence, a Compose example, and file ownership for the image's UID1001.